Detachable mini-camera device

ABSTRACT

Integrated but detachable mini-camera for a mobile device. The mobile device comprises a main body and a detachable mini-camera configured to attach to and detach from a socket in the main body. The detachable mini-camera may comprise at least one camera and a rechargeable battery configured to, while the detached mini-camera is attached to the main body, charge from a battery in the main body via the socket. While the detachable mini-camera is detached from the main body, a wireless transceiver in the detachable mini-camera wirelessly communicates with a wireless transceiver in the main body, and a mobile application, executed by a processor in the main body, controls the detachable mini-camera and receives image data from the detachable mini-camera via the wireless communication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent App. No.62/608,788, filed on Dec. 21, 2017, which is hereby incorporated hereinby reference as if set forth in full.

BACKGROUND Field of the Invention

The embodiments described herein are generally directed to a camera,and, more particularly, to an integrated mini-camera device that can bedetached from and attached to the main body of a larger device, such asa smartphone or other mobile computing device.

Description of the Related Art

Many, if not most, mobile devices these days are outfitted with one ormore built-in or embedded cameras. Examples of such mobile devicesinclude, without limitation, cellular or other wireless telephones(e.g., smartphones), tablet personal computers (PCs), laptop PCs,wearable devices (e.g., smart watches) and any other type of mobile(e.g., wireless) user equipment. Typically, the built-in camera is asmall-complementary-metal-oxide-semiconductor (CMOS) based orcharge-coupled-device (CCD) based image sensor that comprises associatedcontrol components and electronics.

A user of the mobile device can use the built-in camera to capturehigh-resolution digital photographs and videos, similarly to atraditional digital camera. For a rear-facing camera in which thecomponents (e.g., camera, flash, and sensor) are on the rear side of themobile device, the user typically faces the rear side of the mobiledevice towards the object of interest and actuates a control on themobile device (e.g., virtual button within a graphical user interfacedisplayed on a front display of the mobile device, hard key on the frontor side of the mobile device, etc.) to capture a photograph or video ofthe object. The mobile device then stores the photograph or video as adigital image file (e.g., a Joint Photographic Experts Group (JPEG)file) in a memory of the mobile device.

Generally, the user can utilize software on the mobile device toorganize, edit, transmit, and/or share the captured digital photographor video files. For example, the digital file may be transmitted via awireless communications network (e.g., cellular network, Wi-Fi™ network,etc.) to a cloud-computing service, to another device (e.g., associatedwith another user or the same user), and/or the like. In the case of avideo, the user may conduct a video conference (e.g., via FaceTime™,Skype™, or other application). Alternatively, the user may live-stream avideo to an online service (e.g., social media platform, such asFacebook™) via the wireless communication network. Other users may thenview the live-stream of the video via a data connection with the onlineservice. As another alternative, one user could live-stream a videodirectly from his or her mobile device to another user's device.

Since the inception of the camera phone in 1997, users have becomeincreasingly comfortable using the built-in cameras of their mobiledevices as a primary camera for photographs and video, in place oftraditional stand-alone handheld cameras. Thus, manufacturers have begundesigning their mobile devices to enhance the quality, usability, andfunctionality of the built-in cameras. However, built-in cameras remaindifficult to use in conjunction with other functions of the mobiledevices.

For example, when the need arises to use the built-in camera to capturea photograph or video while a user is engaged in a telephoneconversation using the mobile device, the user must generally interruptthe telephone conversation to position the mobile device for thecapture. Specifically, the user may need to switch the telephoneconversation to speakerphone, in order to enable appropriate positioningof the mobile device for photograph or video capture. In addition, theuser must maintain the mobile device within a comfortable range of theuser's ears and mouth, in order to continue the telephone conversationwhile attempting to capture a photograph or video. It also results in aloss of privacy, since both sides of the conversation may be heard bypasserby's. In addition, the user may need to navigate to a camerafunction of the mobile device (e.g., using a touch panel display of themobile device) in order to initiate the capture of the photograph orvideo.

What is needed is an integrated but detachable mini-camera that can bedetached from the main body of a mobile device and used to capturephotographs and video without regard for the orientation of the mainbody. Ideally, the mini-camera could be reattached to the main body ofthe mobile device for recharging and compact, integrated storage of themini-camera.

SUMMARY

Accordingly, a mini-camera is disclosed that is capable of quick andeasy undocking and docking with a main body of a mobile device. In anembodiment, a mobile device is disclosed that comprises: a main bodycomprising a battery, a first wireless transceiver, a socket, at leastone hardware processor, a memory, and a mobile application stored in thememory; and a detachable mini-camera configured to attach to the socketand detach from the socket, wherein the detachable mini-camera comprisesat least one camera, a rechargeable battery configured to charge fromthe battery in the main body when the detachable mini-camera is attachedto the socket, and a second wireless transceiver configured towirelessly communicate with the first wireless transceiver in the mainbody when the detachable mini-camera is detached from the socket;wherein the mobile application is configured to, when executed by the atleast one hardware processor in the main body, when the detachablemini-camera is detached from the socket, wirelessly communicate with thedetachable mini-camera, via the first and second wireless transceivers,to control the detachable mini-camera and receive image data captured bythe detachable mini-camera. The detachable mini-camera may furthercomprise at least one sensor and at least one flash. The main body mayfurther comprise: a front surface comprising a touch panel display; anda rear surface comprising the socket, wherein the rear surface is on anopposite side of the main body as the front surface. The at least onecamera may consist of a single camera configured to capture photographsand video, or may comprise a first camera dedicated to capturingphotographs and a second camera dedicated to capturing video (e.g.,comprising a plurality of image frames).

The at least one camera may comprise: a mini-camera device; and at leastone motor powered by the rechargeable battery in the detachablemini-camera and configured to rotate the mini-camera within a range ofrotation around at least one axis. The at least one camera may furthercomprise a rod, wherein the at least one motor comprises a ball-and-axismotor that is attached to a first end of the rod, wherein themini-camera device is attached to a second end of the rod that isopposite to the first end, and wherein the ball-and-axis motor isconfigured to, when activated, rotate the rod, so as to rotate themini-camera within the range of rotation around a first axis that iscoincident with a longitudinal axis of the rod. Additionally oralternatively, the mini-camera device may comprise an imaging face on afront side and a motor on a rear side, opposite the imaging face,wherein the motor is configured to rotate the imaging face within arange of rotation around a second axis that is orthogonal to thelongitudinal axis of the rod.

In an embodiment, the mobile application is configured to: generate agraphical user interface that comprises one or more inputs for movingthe mini-camera device; and, in response to receiving a user operationof at least one of the one or more inputs, transmit a control commandfrom the first wireless transceiver in the main body to the secondwireless transceiver in the detachable mini-camera, so as to actuate theat least one motor to rotate the mini-camera device in accordance withthe control command. The mobile application may be further configuredto: generate a graphical user interface that comprises one or moreinputs for specifying an object in a photograph; and, when an object isspecified, generate a reference representation of the object, and duringa subsequent video recording or live stream in which the mobileapplication receives a plurality of image frames from the detachablemini-camera, detect the object in one or more of the plurality of imageframes, and, in response to detecting the object, transmit a controlcommand from the first wireless transceiver in the main body to thesecond wireless transceiver in the detachable mini-camera, so as toactuate the at least one motor to rotate the mini-camera device to trackthe object.

In an embodiment, the mobile application is configured to: generate agraphical user interface that comprises a real-time-view region and atleast one input for one or more of capturing a photograph, initiating avideo recording, and initiating a live stream, wherein thereal-time-view region comprises real-time image data captured by thedetachable mini-camera and wirelessly transmitted from the secondwireless transceiver in the detachable mini-camera to the first wirelesstransceiver in the main body; and, in response to receiving a useroperation of the at least one input, transmit a control command from thefirst wireless transceiver in the main body to the second wirelesstransceiver in the detachable mini-camera, so as to actuate the at leastone camera in the detachable mini-camera according to the controlcommand. The mobile application may be configured to, when the useroperation of the at least one input is to capture a photograph: generatethe control command to capture the photograph; receive the photographfrom the detachable mini-camera via a wireless communication from thesecond wireless transceiver to the first wireless transceiver; and storethe received photograph in the memory in the main body. The mobileapplication may be configured to, when the user operation of the atleast one input is to initiate a video recording: generate the controlcommand to initiate the video recording; during the video recording,receive a plurality of image frames from the detachable mini-camera viaa wireless communication from the second wireless transceiver to thefirst wireless transceiver; and store the received plurality of imageframes in the memory in the main body as a video file. The mobileapplication may be configured to, when the user operation of the atleast one input is to initiate a live stream: generate the controlcommand to initiate the live stream; and, during the live stream,receive a plurality of image frames from the detachable mini-camera viaa wireless communication from the second wireless transceiver to thefirst wireless transceiver, and relay the plurality of image frames to asharing platform via at least one wireless cellular network. Inaddition, the mobile application may be further configured to: generatea graphical user interface that comprises one or more inputs foridentifying a group of one or more contacts; and, for each of the one ormore contacts in the group, transmit an invitation to the contact,wherein the invitation comprises information for viewing the livestream. Alternatively or additionally, the mobile application may befurther configured to generate a graphical user interface that comprisesone or more inputs configured to receive a user selection of the sharingplatform.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of the present invention, both as to its structure andoperation, may be gleaned in part by study of the accompanying drawings,in which like reference numerals refer to like parts, and in which:

FIGS. 1A-1C illustrate an example mobile device with a detachablemini-camera, according to embodiments;

FIGS. 2A and 2B illustrate a detachable mini-camera, according toembodiments;

FIGS. 3A and 3B illustrate components of a detachable mini-camera,according to an embodiment;

FIGS. 4A-4H illustrate various screens of an example graphical userinterface of a mobile application for controlling a detachablemini-camera, according to an embodiment; and

FIG. 5 illustrates an example processing system, by which one or more ofthe processes described herein (e.g., implemented by the mobileapplication), may be executed, according to an embodiment.

DETAILED DESCRIPTION

In an embodiment, a mini-camera is disclosed that is capable of quickand easy undocking and docking with a main body of a mobile device.After reading this description, it will become apparent to one skilledin the art how to implement the invention in various alternativeembodiments and alternative applications. However, although variousembodiments of the present invention will be described herein, it isunderstood that these embodiments are presented by way of example andillustration only, and not limitation. As such, this detaileddescription of various embodiments should not be construed to limit thescope or breadth of the present invention as set forth in the appendedclaims.

1. Detachable Mini-Camera

FIG. 1A illustrates an example mobile device with a detachablemini-camera of a first embodiment in an attached state (e.g., dockedstate), whereas FIG. 1B illustrates an example mobile device with adetachable mini-camera of a second embodiment in the attached state.Mobile device 100 is illustrated as a smartphone. However, mobile device100 may comprise any type of mobile computing device, including asmartphone, tablet PC, laptop PC, and/or the like, which may comprise orbenefit from an integrated camera. Typically, mobile device 100 willutilize wireless communications, such as cellular communications (e.g.,via a Long Term Evolution (LTE) network) and/or Wi-Fi™ communications,to communicate with other devices over one or more wireless and/orwired, public and/or private networks, including, for instance, theInternet.

Mobile device 100 comprises a detachable mini-camera 150. While attachedto mobile device, detachable mini-camera 150 may act in the same manneras any built-in camera. As illustrated, in the attached state,detachable mini-camera 150 is a rear-facing camera that is attached tothe rear surface of mobile device 100. The rear surface is, for example,a surface that is on an opposite side of mobile device 100 as a displayand/or inputs (e.g., a touch panel display) of mobile device 100.Alternatively or in addition to a detachable mini-camera 150 on the rearsurface, mobile device 100 may comprise a detachable mini-camera 150attached to the front surface of mobile device 100 (e.g., on the samesurface as the display of mobile device 100). When attached to mobiledevice 100, detachable mini-camera 150 may be rear-facing (e.g., whenattached to the rear surface of mobile device 100, or alternativelythrough the rear surface while attached via the front surface) orfront-facing (e.g., when attached to the front surface of mobile device100, or alternatively through the front surface while attached via therear surface). As another alternative, detachable mini-camera 150 couldcomprise both rear and front surfaces of mobile device 100 (e.g., anentire detachable corner of mobile device 100, detachable top of mobiledevice 100, detachable side of mobile device 100, etc.).

FIG. 1C illustrates an example mobile device with a detachablemini-camera in a detached state (e.g., undocked state), according to anembodiment. Specifically, detachable mini-camera 150 has been detachedfrom mobile device 100, exposing a socket 110 within the surface ofmobile device 100. Socket 110 may comprise grooves, hooks, magnets,and/or other attachment components that detachably engage withcorresponding attachment components on detachable mini-camera 150 (e.g.,on the rear surface of detachable mini-camera 150), such that detachablemini-camera 150 can be easily and intuitively detached from socket 100and attached to socket 100. In addition, socket 110 may comprise one ormore electrical traces or other connectors that conductively couple withone or more corresponding electrical traces or other connectors ondetachable mini-camera 150 (e.g., on the rear surface of detachablemini-camera 150) while the attachment components are engaged to attachdetachable mini-camera 150 to mobile device 100. Again, while the rearsurface of mobile device 100 is illustrated, alternatively oradditionally, socket 110 may be formed in the front surface of mobiledevice 100 or another surface of mobile device 100. Furthermore, whiledetachable mini-camera 150A of the first embodiment is illustrated inFIG. 1C, the illustrated socket 110 can be used with or adapted fordetachable mini-camera 150B of the second embodiment or any otherembodiment of detachable mini-camera 150.

In the detached state, illustrated in FIG. 1C, detachable mini-camera150 acts as a stand-alone camera that wirelessly communicates withmobile device 100. Specifically, detachable mini-camera 150 may comprisea transmitter that wirelessly transmits signals, encoding data, to areceiver in the main body of mobile device 100. For example, whiledetached from mobile device 100, detachable mini-camera 150 maywirelessly transmit captured image data (e.g., photographs, videorecordings, live streams, etc.) to mobile device 100 (e.g., for storage,viewing, or other processing at mobile device 100), in real time as theimage data is captured. As used herein, the noun “real time” and theadjective “real-time” refer to instances of both real time and near-realtime (e.g., within milliseconds or a second from actual real time asdetermined by processing latency, network latency, and/or othercommunication latency). In addition, detachable mini-camera 150 maycomprise a receiver that wirelessly receives signals from a transmitterof mobile device 100. In an embodiment, the detachable mini-camera 150and/or mobile device 100 may comprise a transceiver that comprises boththe transmitter and the receiver. Any wireless technology may be usedfor the wireless communication between detachable mini-camera 150 andmobile device 100, including, without limitation, Bluetooth™ Zigbee™,and/or the like.

In an embodiment, socket 110 comprises one or more electrical connectorsthat supply power to detachable mini-camera 150 in the attached state.Accordingly, detachable mini-camera 150 may comprise a rechargeablebattery that, in the attached state in which detachable mini-camera 150is attached to mobile device 100 via socket 110, is charged from abattery or other power supply of mobile device 100 via the electricalconnectors in socket 110.

In an embodiment, socket 110 also comprises one or more electricalconnectors that convey communication signals between detachablemini-camera 150 and mobile device 100. These electrical connector(s) maybe the same as or different than the electrical connector(s) that supplypower to detachable mini-camera 150. Thus, in the attached state,illustrated in FIGS. 1A and 1B, detachable mini-camera 150 maycommunicate with mobile device 100 via one or more direct electricalconnections to socket 110. Alternatively, detachable mini-camera 150could wirelessly communicate with mobile device 100 even in the attachedstate, in the same or similar manner as in the detached state. However,such an embodiment would likely result in higher battery consumption dueto the operation of the wireless transceivers in both the detached andattached states.

FIG. 2A illustrates the components of detachable mini-camera 150A of thefirst embodiment illustrated in FIG. 1A, whereas FIG. 2B illustrates thecomponents of detachable mini-camera 150B of the second embodimentillustrated in FIG. 1B. Generally, detachable mini-camera 150 comprisesa housing 152 configured to house one or more cameras 154, one or moresensors 156, and/or one or more flashes 158, as well as their associatedor auxiliary electronic components.

In the first embodiment, illustrated in FIG. 2A, detachable mini-camera150A comprises one camera 154, one sensor 156, and one flash 158. Thisfirst embodiment corresponds more closely to traditional mobile cameras,with a single camera 154 positioned in the center of detachablemini-camera 150A, a single sensor 156 positioned on a first side ofcamera 154 (e.g., illustrated on the right side), and a single flash 158positioned on a second side of camera 154 that is opposite to the firstside (e.g., illustrated on the left side). Camera 154 may be capable ofcapturing both photographs and video recordings.

In the second embodiment, illustrated in FIG. 2B, detachable mini-camera150B comprises two cameras 154A and 154B, one sensor 156, and one flash158. In this second embodiment of detachable mini-camera 150B, cameras154A and 154B may be identical or different in structure and/orfunction, and may operate independently from each other and/or in unisonwith each other. As one example, camera 154A may be a photographiccamera dedicated to capturing photographs, whereas camera 154B is avideo camera dedicated to capturing video (e.g., comprising a pluralityof image frames). In the illustrated embodiment, sensor 156 ispositioned equidistant between camera 154A and camera 154B, and flash158 is positioned below sensor 156 and equidistant from camera 154A andcamera 154B. However, other arrangements are possible.

In an embodiment, each camera 154 is capable of moving with respect toone or more axes. For example, as illustrated in FIGS. 2A and 2B, eachcamera 154 is capable of rotating around both an X-axis and a Y-axis.Alternatively, each camera may only be capable of rotating around oneaxis (e.g., the Y-axis) or may be fixed (i.e., not capable of rotationor other movement). In an embodiment in which camera 154 rotates,housing 152 may comprise, for each camera 154, an opening or recesswhich is configured to receive camera 154 while allowing camera 154 torotate around the one or more axes without the camera's field of viewbeing blocked by any portion of housing 152. Alternatively oradditionally, the angle of rotation of camera 154 may be limited suchthat the camera's field of view will never be blocked by any portion ofhousing 152.

In an embodiment, sensor 156 is a separate component that is insetwithin an opening or recess of housing 152. Sensor 156 may comprise asensor for detecting luminance, movement, proximity, and/or the like.Output from sensor 156 may be used to determine controls for camera(s)154, flash 158, and/or other components of detachable mini-camera 150.

In an embodiment, flash 158 provides a flash or pulse of light forlighting the environment while an image or video is being captured bycamera 154. Flash 158 may be controlled automatically by a mobileapplication executing on mobile device 100 and/or manually by a user ofthe mobile application. For example, a user may specify a specific flashmode within a graphical user interface of the mobile application, suchas “automatic”, “on”, “off”, “indoor”, “outdoor”, and/or the like. Inthe “automatic” mode, the mobile application may automatically utilizeflash 158 when sensor 156 detects a low level of luminance (e.g.,indicating a dark environment), while not utilizing flash 158 whensensor 156 detects a high level of luminance (e.g., indicating a brightenvironment). The mobile application could also automatically determineand utilize flash 158 at a plurality of different brightness levelsdepending on the level of luminance (e.g., higher brightness levels forlower levels of luminance, and lower brightness levels or no flash forhigher levels of luminance). In the “on” mode, the mobile applicationmay always utilize flash 158, regardless of any output from sensor 156indicating a luminance of the environment. In the “off” mode, the mobileapplication may never utilize flash 158, regardless of any output fromsensor 156 indicating a luminance of the environment. In the “indoor”mode, the mobile application may utilize flash 158, as in the“automatic” mode (i.e., depending on the luminance of the environmentdetected by sensor 156), but using a low-light flash level (i.e., lesslight than in the “outdoor” mode). In the “outdoor” mode, the mobileapplication may utilize flash 158, as in the “automatic” mode (i.e.,depending on the luminance of the environment detected by sensor 156),but using a bright-light flash level (i.e., more light than in the“indoor” mode).

In an embodiment, housing 152 of detachable mini-camera 150 (e.g., 150Aand/or 150B) may comprise one or more fastening mechanisms, configuredto attach detachable mini-camera 150 to socket 110 of mobile device 100,as well as other objects (i.e., objects other than mobile device 100).For example, housing 152 may comprise a spring-loaded clip or clasp thatis capable of being press-opened and biased by a spring to snap closedaround an object. The object in this case may comprise clothing (e.g.,the collar, pocket, or lapel of a shirt of jacket, the waist of pants, abelt, etc.), accessories (e.g., purse, glasses, etc.), and/or anythingelse that can fit within the grasp of the clip. Additionally oralternatively, housing 152 may comprise other fastening mechanisms(e.g., magnets, Velcro™, snaps, loops, etc.).

FIG. 3A illustrates the components of camera 154, according to anembodiment. As illustrated, camera 154 comprises a mini-camera device310 that is attached to a rod 320. Rod 320 is rotated by a ball-and-axismotor 330 that is powered, for example, by a rechargeable battery withinhousing 152 of detachable mini-camera 150.

In an embodiment, ball-and-axis motor 330 comprises an independent motorwithin a base (e.g., cylindrical or cubical base) that is fixed directlyor indirectly to housing 152. The motor rotates or spins in eitherdirection (e.g., clockwise and counterclockwise) around an axis that iscoincident with the longitudinal axis of rod 320. The range of rotationof ball-and-axis motor 330 may be limited (e.g., to a fixed arc definedby an angle of rotation) to prevent full rotation.

In an embodiment, rod 320 is a long, thin, substantially cylindrical,but pin-shaped rod. Rod 320 may be positioned to extend along itslongitudinal axis from a center of the base of ball-and-axis motor 330.Rod 320 may be fixed to ball-and-axis motor 330, such that it rotateswith ball-and-axis motor 330, for example, within the same range ofrotation as ball-and-axis motor 330.

In an embodiment, mini-camera device 310 is attached to rod 320 at ornear an end of rod 320 that is opposite the end of rod 320 fixed toball-and-axis motor 330. For example, mini-camera device 310 may bepositioned on the tip of rod 320. In other words, one end of rod 320 isattached to ball-and-axis motor 330, and the other end of rod 320 isattached to mini-camera device 310. Thus, as ball-and-axis motor 330rotates, rod 320 rotates due to its attachment to ball-and-axis motor330, and this, in turn, causes mini-camera device 310 to rotate to thesame degree as ball-and-axis motor 330 and rod 320. Consequently, if therange of rotation of ball-and-axis motor 330 and rod 320 are limited,the range of rotation of mini-camera device 310 is similarly limited.

In an embodiment, the range of rotation of the imaging face ofmini-camera device 310 may comprise rotation in both a rotationaldirection around the longitudinal axis of rod 320 (e.g., axis Y in FIGS.2A and 2B) as well as a rotational direction around an axis that isorthogonal to the longitudinal axis of rod 320 (e.g., axis X in FIGS. 2Aand 2B). In other words, mini-camera device 310 may rotate left andright as well as up and down to reposition the camera face at any of aplurality of orientations within the range of rotation. For example, thebackside of mini-camera device 310 may comprise a small motor, which,when activated, rotates the imaging face of mini-camera device 310around the X axis that is orthogonal to the longitudinal Y axis of rod320 (e.g., up and down with respect to the longitudinal Y axis of rod320). In this manner, the range of rotation of imaging face ofmini-camera device 310 may be nearly spherical or hemispherical (e.g.,180° around the longitudinal Y axis of rod 320 and 180° around theorthogonal X axis). An electrical connection (e.g., conductive trace,cable, etc.), for supplying power and/or control to the small motor, maybe fed to the small motor through a hollow center of rod 320 and/orball-and-axis motor 330, or alternatively may be external to rod 320and/or ball-and-axis motor 330.

FIG. 3B illustrates the components of detachable mini-camera 150A,according to an embodiment. Detachable mini-camera 150B of the secondembodiment may be implemented in a similar manner. Specifically, housing152 comprises one or more internal and/or external recesses that areconfigured to receive one or more cameras 154, one or more sensors 156,one or more flashes 158, an electronics bed 340, one or morerechargeable batteries 350, one or more transceivers 360, and/or theirassociated or auxiliary components. During the manufacturing process,each component may be inserted into its corresponding recess, directlyor indirectly fixed to housing 152, and conductively connected to othercomponents via electrical connectors (e.g., 370) within housing 152(e.g., within electronics bed 340). In addition, each of the camera(s)154, sensor(s) 156, flash(es) 158, and/or transceiver(s) 360, may beconductively connected to rechargeable battery 350 (e.g., viaelectronics bed 340) so as to be powered by rechargeable battery 350, atleast when detachable mini-camera 150 is in the detached state.

In an embodiment, electronics bed 340 comprises a thin substrate ofstrengthened material to which the electronic components of detachablemini-camera 150 are attached. The electronic components may also beelectrically coupled via electronics bed 340 (e.g., via cables and/orelectrical traces and/or other connectors within electronics bed 340).Electronics bed 340 is affixed to and/or otherwise seated within housing152.

In an embodiment, rechargeable battery 350 comprises a lithium-ionbattery (e.g., a micro 1A lithium-ion battery), which is seated inelectronics bed 340 and charged by a charging module. The chargingmodule may comprise one or more electrically conductive traces that, inthe attached state, conductively contact a corresponding number ofelectrically conductive traces in socket 110 of mobile device 100, whichare, in turn, conductively coupled to a battery of mobile device 100.Thus, when detachable mini-camera 150 is attached to mobile device 100via socket 110, power is supplied from the battery of mobile device 100to the electrically conductive traces of socket 110, and through theconductive contact, to the electrically conductive traces of thecharging module, which relay the power to rechargeable battery 350, soas to charge rechargeable battery 350. Then, when detachable mini-camera150 is detached from mobile device 100, rechargeable battery 350 isdischarged to power the components of detachable mini-camera 150.Additionally or alternatively, the charging module may comprise a powersocket (e.g., compliant with an industry standard, such as a UniversalSerial Bus (USB) port) configured to receive power via an end of a powercable. In this case, rechargeable battery 350 may be charged from anypower supply to which the other end of the power cable is attached(e.g., wall outlet, mobile backup battery, other electronic device,etc.).

In an embodiment, transceiver 360 is conductively coupled to electronicsbed 340 and powered by rechargeable battery 340. Transceiver 360 maycomprise a Bluetooth™ transceiver (e.g., a mini slave wirelessBluetooth™ 4.0 or 5.0 transceiver), which is capable of pairing with aBluetooth™-capable transceiver of another device, such as mobile device100. Bluetooth™ 5.0 supports a wireless communication range of 50-100feet. However, wireless technologies, other than Bluetooth™ and/or withdifferent wireless communication ranges can be used, and transceiver 360may be capable of wireless communication using a plurality of differenttechnologies (e.g., including Bluetooth™, Wi-Fi™, Zigbee™, and/or thelike), using a plurality of frequency bands, and/or within a pluralityof different wireless communication ranges.

In an embodiment, transceiver 360 is electrically coupled to a flexcable antenna 362, which is used transmit wireless signals, representingdata (e.g., image data captured by mini-camera device(s) 310), to awireless receiver in mobile device 100, and/or receive wireless signals,representing data (e.g., control commands generated by mobile device100), from a wireless transmitter in mobile device 100. Transceiver 360may also be capable of receiving signals from Global Positioning System(GPS) satellites via flex cable antenna 362, for the purposes ofdetermining a location of detachable mini-camera 150. For example, flexcable antenna 362 may comprise a Bluetooth™-GPS-Wi-Fi™ flex cableantenna that is capable of communicating via Bluetooth™ and Wi-Fi™ andreceive GPS signals. Regardless of the specific wireless technology ortechnologies used, transceiver 360 may comprise an encoder configured toencode data (e.g., image data from camera 154) into a radio signal to betransmitted via flex cable antenna 362, and a decoder configured todecode data from a radio signal that has been received via flex cableantenna 362. The main body of mobile device 100 may comprise anidentical, similar, or different transceiver having the samecapabilities.

In an embodiment, once detachable mini-camera 150 is detached fromsocket 110 in mobile device 100, transceiver 360 automatically pairs(e.g., via Bluetooth™) with a transceiver in mobile device 100 to beginwireless communication with mobile device 100. Conversely, oncedetachable mini-camera 150 is attached to socket 110 in mobile device100, transceiver 360 may automatically un-pair with the transceiver inmobile device 100 to end wireless communication with mobile device 100(e.g., to reduce power consumption). Alternatively, detachablemini-camera 150 may always remain paired with the transceiver in mobiledevice 100 to perform wireless communication with mobile device 100,regardless of whether or not it is attached or detached from socket 110(e.g., at the cost of increased power consumption). In either case, thewireless communication may comprise transceiver 360 transmitting data(e.g., image data, status data, etc.), collected by detachablemini-camera 150, to mobile device 100 (e.g., for processing by themobile application described elsewhere herein), and receiving data(e.g., control commands, configuration data, etc.) from mobile device100 (e.g., generated by the mobile application executing on mobiledevice 100).

In an embodiment, various components of detachable mini-camera 150 areelectrically connected to each other within electronics bed 340 via oneor more electrically conductive substrates or cables. For example,electronics bed 340 may comprise one or more flex cables 370 that coupleto each camera 154, sensor 156, and/or flash 158. Each flex cable 370may comprise a thin strip of fibrous and conductive material thatsupplies power (e.g., by relaying power from rechargeable battery 350)to camera, 154, sensor 156, and/or flash 158. In addition, flex cable(s)370 may transmit control signals to camera 154, sensor 156, and/or flash158 and/or receive signals from camera 154, sensor 156, and/or flash158. For instance, in an embodiment, camera 154 may receive controlsignals, provide an output (e.g., image data), and receive power (e.g.,to power ball-and-axis motor 330) via a first flex cable, sensor 156 mayprovide a sensor output and receive power via a second flex cable 370,and flash 158 may receive control signals (e.g., specifying when and/orhow bright to flash) and receive power (e.g., to be converted into apulse of light) via a third flex cable 370.

In an embodiment, detachable mini-camera 150 may also comprise one ormore processors (not shown). Each processor may comprise a centralprocessing unit (CPU) that communicates with one or more of camera(s)154, sensor(s) 156, flash(es) 158, and/or transceiver(s) 360 via one ormore electrical connections (e.g., flex cables) on electronics bed 240.The processor may receive messages from the connected components,process the information in the messages, and/or control the connectedcomponents based on processed information. For example, the processormay receive control information (e.g., comprising control commandsand/or configuration information), received and decoded by transceiver360, and/or sensor output from sensor 156, and control one or morecameras 154 and/or flash 158 based on the control information. Thecontrol of a camera 154 may comprise moving the face of mini-cameradevice 310 by activating ball-and-axis motor 330, capturing a photographand/or video, setting an exposure time during image capture (e.g.,photograph and/or video capture), and/or controlling any other functionor setting of camera 154. The control of flash 158 may comprise settinga light level, activating the flash to trigger a pulse of light (e.g.,according to a set brightness level) during image capture, preventingactivation of the flash in a low-light setting (e.g., as detected bysensor 156), and/or the like.

2. Mobile Application

In an embodiment, a mobile application is provided. The mobileapplication may be pre-installed on mobile device 100, for example, bythe original equipment manufacturer (OEM). Additionally oralternatively, the mobile application may be a stand-alone applicationthat is downloadable from an application store or other network site(e.g., website) for one or more operating systems (e.g., iOS™, Android™,Microsoft Windows™, etc.).

The mobile application may be stored and executed by a processor ofmobile device 100 to control the functions and/or settings of detachablemini-camera 150. For example, the mobile application may generate agraphical user interface comprising one or more screens that eachcomprise one or more inputs that enable a user to control variousfunctions or settings of detachable mini-camera 150. The screens of thegraphical user interface may be navigable in any known manner, forexample, using virtual buttons, touch gestures (e.g., taps, longpresses, swipes, flicks, pinch-ins, pinch-outs, etc.).

FIGS. 4A-4H illustrate one or more screens of a graphical user interface400, generated by a mobile application executing on mobile device 100,according to an embodiment. Each screen may comprise one or moreregions, implemented as frames and/or the like. Graphical user interface400 may be displayed on a display of mobile device 100. In theillustrated embodiments, the display of mobile device 100 is integratedinto a front surface of mobile device 100. It should be understood that,in these embodiments, socket 110, which receives detachable mini-camera150, is either detached or attached on the opposite and rear surface ofmobile device 100, and therefore, is not visible in FIGS. 4A-4H.

2.1. Main Screen

FIG. 4A illustrates a main screen (e.g., home or landing screen) ofgraphical user interface 400 of the mobile application, according to anembodiment. The main screen comprises a real-time-view region 405, whichdisplays image data representing a real-time, optical field of view ofcamera 154 in detachable mini-camera 150. In the illustrated example,detachable mini-camera 150 may be detached from mobile device 100, inwhich case transceiver 360 is wirelessly transmitting the real-timeoptical field of view captured by camera 154 to mobile device 100, inreal time. Alternatively, detachable mini-camera 150 may be attached tomobile device 100 via socket 110 on the rear surface of mobile device100, in which case the real-time optical field of view captured bycamera 154 may be non-wirelessly transferred from detachable mini-camera150 to mobile device 100, in real time, via an electrical connection tosocket 110. It should be understood that the entire graphical userinterface 400 (e.g., illustrated in FIGS. 4A-4H) may be identicalregardless of whether detachable mini-camera 150 is in the attachedstate or the detached state. In other words, graphical user interface400 is no different when detachable mini-camera 150 is detached thanwhen detachable mini-camera 150 is attached. However, an indication(e.g., icon and/or text) that detachable mini-camera 150 is detached maybe displayed within graphical user interface 400 when detachablemini-camera 150 is detached and/or an indication (e.g., icon and/ortext) that detachable mini-camera 150 is attached may be displayedwithin graphical user interface 400 when detachable mini-camera 150 isattached. Thus, advantageously, a user can easily determine whether thedetachable mini-camera 150 is attached or detached without having tochange the orientation of mobile device 100 or the user's perspective ofmobile device 100 (e.g., in order to check the rear surface of mobiledevice 100). In addition, as discussed elsewhere herein, alerts and/orGPS tracking may be provided when detachable mini-camera 150 isattached, in order to reduce the likelihood that a detached mini-camera150 is lost.

In an embodiment, the main screen also comprises an input region 410(e.g., above or below real-time-view region 405). Input region 410comprises one or more inputs for initiating a function of detachablemini-camera 150. For example, input region 410 may comprise inputs forinitiating capture of a photograph, initiating a video recording,initiating a live stream (e.g., to a social media platform) of the imagedata being captured by detachable mini-camera 150, and/or invitingcontact(s) to a group (e.g., for sharing a live stream).

2.2. Capturing Image Data

FIG. 4B illustrates a photograph screen of graphical user interface 400of the mobile application, according to an embodiment. The photographscreen may be displayed when a user selects the input for initiatingcapture of a photograph in the main screen or other screen of graphicaluser interface 400. As illustrated, the photograph screen comprisesreal-time-view region 405. In addition, the photograph screen comprisesan input region 415, which comprises one or more inputs for utilizingthe photograph function of detachable mini-camera 150. For example,input region 415 may comprise inputs for zooming in (e.g., increasing amagnification of camera 154) and zooming out (e.g., decreasing amagnification of camera 154), inputs for rotating camera 154 in two ormore directions (e.g., by activating a ball-and-axis motor 330 in camera154), and/or an input for capturing a photograph. In the illustratedexample, the input for capturing the photograph is a relatively largecircular icon positioned in the center of input region 415 (e.g., with a“P” or other indication that detachable mini-camera 150 is in a mode forcapturing photographs), with an input for zooming in above the circularicon, an input for zooming out below the circular icon, an input forrotating camera 154 to the left on the left side of the circular icon,and an input for rotating camera 154 to the right on the right side ofthe circular icon. Thus, a user can easily set the magnification andangle of camera 154 and capture a photograph at those settings. Itshould be understood that input region 415 could also comprise inputsfor other settings, such as a flash setting, exposure setting, rotatingor moving camera 154 in other directions (e.g., up and down), and/or thelike.

FIG. 4C illustrates a video screen of graphical user interface 400 ofthe mobile application, according to an embodiment. The video screen maybe displayed when a user selects the input for initiating a videorecording in the main screen or other screen of graphical user interface400. As illustrated, the video screen comprises real-time-view region405. In addition, the video screen comprises an input region 420, whichcomprises one or more inputs for utilizing the video recording functionof detachable mini-camera 150. For example, input region 420 maycomprise an input for starting and stopping a video recording. In theillustrated example, the input for starting and stopping a videorecording is a circular icon positioned in the center of input region420 (e.g., with a “V” or other indication that detachable mini-camera150 is in a mode for capturing video recordings). When no video iscurrently being recorded, a user may select the input to start a newvideo recording. Then, while a video is being recorded, a user mayselect the same input to stop the new video recording. When the videorecording is stopped, the video recording may be automatically savedinto a memory of mobile device 100. It should be understood that theinput may change depending on whether or not a video is currently beingrecorded (e.g., the color of the icon may change between gray and red,the shape of the icon may change, etc.).

During recording of a video, image frames may be transmitted fromdetachable mini-camera 150 to mobile device 100 in real time and storedin a memory of mobile device 100. Thus, when the video recording isstopped, the accumulated image frames may be stored in a video file onmobile device 100. Additionally, the image frames may be accumulated ina memory of detachable mini-camera 150. In this case, in an alternativeembodiment, when the video recording is stopped, a processor ofdetachable mini-camera 150 may store the image frames in a video fileand transmit the video file to mobile device 100 for storage.

FIG. 4D illustrates a live-stream screen of graphical user interface 400of the mobile application, according to an embodiment. The live-streamscreen may be displayed when a user selects the input for initiating alive stream in the main screen or other screen of graphical userinterface 400. As illustrated, the live-stream screen comprisesreal-time-view region 405. In addition, the live-stream screen comprisesan input region 425, which comprises one or more inputs for utilizingthe live-stream function of detachable mini-camera 150. For example,input region 425 may comprise an input for starting and stopping a livestream. In the illustrated example, the input for starting and stoppinga live stream is a circular icon positioned in the center of inputregion 425 (e.g., with an “L” or other indication that detachablemini-camera 150 is in a mode for capturing a live stream). When no livestream is currently being captured, a user may select the input to starta new live stream. Then, while a live stream is being captured, a usermay select the same input to stop the live stream. It should beunderstood that the input may change depending on whether or not a livestream is currently being captured (e.g., the color of the icon maychange between gray and red, the shape of the icon may change, etc.).Additionally or alternatively, another indication (e.g., a green circle)may be displayed (e.g., in the far left of input region 425) while alive stream is being captured.

During a live stream, image frames may be transmitted from detachablemini-camera 150 to mobile device 100 in real time. In addition tocontinuously and sequentially displaying the image frames inreal-time-view region 405, mobile device 100 may also relay the imageframes, over one or more wireless networks (e.g., a cellular networkproviding access to the Internet), to another device (e.g., anothermobile device) or to a social networking platform to be shared withother devices and/or saved through the social networking platform. Inthis manner, the image frames captured by detachable mini-camera 150 arerelayed through mobile device 100 to another device or to a sharingplatform.

While illustrated with respect to the live-stream screen in FIG. 4D, butnot with respect to the video screen in FIG. 4C, both of these screensmay comprise an input for zooming in (e.g., above the respective inputfor starting and stopping a video recording or live stream), an inputfor zooming out (e.g., below the respective input for starting andstopping a video recording or live stream), an input for rotating camera154 to the left (e.g., on the left side of the respective input forstarting and stopping a video recording or live stream), and an inputfor rotating camera 154 to the right (e.g., on the right side of therespective input for starting and stopping a video recording or livestream). Thus, a user can easily set the magnification and angle ofcamera 154 before and/or during a video recording and/or live stream. Itshould be understood that input regions 420 and/or 425 could alsocomprise inputs for other settings, such as a flash setting, exposuresetting, rotating or moving camera 154 in other directions (e.g., up anddown), and/or the like.

2.3. Sharing Groups

FIG. 4E illustrates a grouping screen of graphical user interface 400 ofthe mobile application, according to an embodiment. The grouping screenmay be displayed when a user selects the input for inviting contact(s)to join a group in the main screen or other screen of graphical userinterface 400. As illustrated, the grouping screen may comprise one ormore inputs for creating groups of contacts for the purposes of sharingimage data captured by detachable mini-camera 150 using the mobileapplication. A user may utilize the input(s) to create a group, name thegroup, and add or invite contacts to the group.

In the illustrated embodiment, the grouping screen comprises anicon-selection region 430 and an input region 435. Icon-selection region430 comprises a plurality of selectable icons. The user can select oneof the plurality of selectable icons (e.g., by tapping the icon in anembodiment which utilizes a touch panel display), and the selected iconwill be assigned to the new group as a pictorial representation of thegroup. Input region 435 comprises a textbox, virtual keyboard, and/orother inputs for specifying a name of the group and identifying one ormore contacts to be added or invited to the group. The contact(s) may beselected from a virtual address book stored in a memory of mobile device100 or entered directly by the user. In an embodiment, mobileapplication sends an invitation for joining the group to each selectedcontact. For example, the invitation may be a Short Message Service(SMS) or Multimedia Messaging Service (MMS) message that is sent by atransmitter of mobile device 100, via one or more data networks, to acellular number of a mobile device of each contact. The invitation maycomprise a link or other element that, when selected by the invitedcontact, initiates a process of joining the group. Alternatively oradditionally, the invitation may prompt the invited contact to reply tothe message in order to accept and/or decline the invitation (e.g.,using a specific keyword to accept the invitation and/or a specifickeyword to decline the invitation). As examples, the user may utilizethe grouping screen to create a “soccer” group for sharing a live streamof a child's soccer game, a “real estate” group for sharing a livestream of an open house that the user is attending, a “car” group forsharing a live stream of the user's car ride, a “cooking” group forsharing a live stream of the user cooking a food dish, and/or the like.

2.4. Object Tracking

FIG. 4F illustrates a tracking function of the mobile application,according to an embodiment. First, the user may capture a photograph ofan object using, for example, the photograph screen or a similar screen.

Second, an object to be tracked may be identified in the capturedphotograph. This identification may comprise the user moving or drawinga polygon (e.g., square) around the object of interest. Alternatively,the mobile application may automatically identify the object ofinterest, for example, using object detection (e.g., facial detection).In the illustrated example, the identified object of interest is theface of the user's daughter who is about to participate in a soccergame. Once the object of interest is identified, the mobile applicationmay generate a representation of the object of interest that can be usedfor subsequent object detection. For instance, the representation of theobject of interest may comprise a feature vector, which comprises aplurality of values that define a set of references features for theobject of interest.

Third, once the object of interest has been identified and convertedinto a reference representation (e.g., a feature vector describing theobject of interest), the mobile application may automatically controldetachable mini-camera 150 to track the object of interest during asubsequent video recording and/or live stream, using real-time objectdetection and tracking within the image frames of the video recording orlive stream. Specifically, detachable mini-camera 150 may capture aplurality of image frames and transmit the captured image frames to themobile application on mobile device 100 in real time. The mobileapplication receives the captured image frames and performs objectdetection (e.g., facial recognition in the illustrated example) on eachimage frame, using the reference representation, as each image frame isreceived. The object of interest is detected whenever an object in theimage frame matches the reference representation. When the object ofinterest is detected within an image frame, its position within thefield of view of camera 154 may be determined and a degree of rotationand/or other distance of movement, required to center the object ofinterest within the field of view of camera 154, may be calculated.Then, the mobile application may transmit a control command totransceiver 360 in detachable mini-camera 150 that instructs the camera154 to rotate according to the calculated degree of rotation and/or moveaccording to the calculated distance of movement. Upon receiving thecontrol command, a processor or other component in detachablemini-camera 150 may control ball-and-axis motor 330 to rotate orotherwise move mini-camera device 310 according to the calculated degreeof rotation and/or distance of movement. In this manner, the mobileapplication controls camera 154 to continually center the object ofinterest within the field of view of camera 154.

Advantageously, this automated object tracking facilitates hands-freevideo recording or live streaming by detachable mini-camera 150. Forinstance, it is contemplated that a user could detach detachablemini-camera 150 from mobile device, and clip or otherwise fastendetachable mini-camera 150 to another object. As long as detachedmini-camera 150 remains within a wireless communication range of mobiledevice 100, the mobile application may continue to control detachedmini-camera 150 and record and/or stream image data captured by detachedmini-camera 150. For example, the user could fasten detached mini-camera150 to a relatively stationary object and continue to use his or hermobile device 100 (e.g., to make or receive telephone calls, send orreceive text messages, browse the Internet, and/or perform any otherconventional function of a mobile device), without having to worry aboutproperly orienting or steadying mobile device 100 to capture the imagedata, or store his or her mobile device 100 (e.g., in a pocket or purse)without having to worry about obscuring the camera. In the illustratedexample, the user is free to relax and watch his or her daughter'ssoccer game without having to hold and move mobile device 100, whiledetached mini-camera 150 properly records or live streams the soccergame and camera(s) 154 track the daughter. In addition, in the case of alive stream, contacts who have joined the sharing group for the livestream may also watch the soccer game on their own devices, without theuser having to worry about the contacts having a negative viewingexperience.

It should be understood that detachable mini-camera 150 may operate inthe same manner, even when attached to mobile device 100 via socket 110.In this case, the mobile application will still control camera(s) 154 torotate and/or otherwise move to track the object of interest, in thesame manner as in the detached state, except, in an embodiment, usingnon-wireless communications. However, because the orientation ofattached mini-camera 150 will depend on the orientation of mobile device100, the user will need to maintain mobile device 100 in a properorientation to ensure proper video recording or live streaming andobject tracking.

2.5. Editing

FIG. 4G illustrates an editing screen of graphical user interface 400 ofthe mobile application, according to an embodiment. The editing screenmay be displayed when a user selects an input for performing editing inthe main screen or other screen of graphical user interface 400. Asillustrated, the editing screen comprises a viewing region 440 forviewing a real-time field of view of detachable mini-camera 150 and/or astored photograph or video recording. In addition, the editing screencomprises an input region 445 for selecting one or more of a pluralityof selectable editing options. The plurality of selectable editingoptions may comprise standard image-processing functions to be performedon the image data in viewing region 440, such as flipping or rotatingthe image data, removing red eye in the image data, modifying a contrastin the image data, modifying a brightness of the image data, croppingthe image data, converting the image data between color andblack-and-white, applying one or more filters to the image data, and/orthe like. The user may be provided with editing options that areavailable via one or both of the mobile application and the manufacturerof mobile device 100.

2.6. Sharing

FIG. 4H illustrates a sharing screen of graphical user interface 400 ofthe mobile application, according to an embodiment. The sharing screenmay be displayed when a user selects an input for specifying settings inthe main screen or other screen of graphical user interface 400. Asillustrated, the sharing screen comprises a plurality of selectablerepresentations of sharing platforms (e.g., social media platforms, suchas Facebook™ Google+™ Twitter™, etc.). The user may select one or moreof the sharing platforms to be used, for example, when live streamingthe image data from detachable mini-camera 150. Thus, the user canpre-select the platform to be used during subsequent live streaming orwhen otherwise sharing image data.

2.7. Detachment Alert

In an embodiment, the mobile application detects and alerts the userwhen detachable mini-camera 150 is detached from mobile device 100. Forexample, socket 110 may comprise a mechanical, magnetic, or electricaldetection sensor to detect whether or not detachable mini-camera 150 iscurrently inserted in socket 110. The mobile application or othersoftware or hardware in mobile device 100 may set a flag whenever thedetection sensor indicates that detachable mini-camera 150 is detached,and the mobile application may provide an alert whenever the flagindicates that detachable mini-camera 150 is detached. The alert maycomprise a visual indication (e.g., a graphical element on a display ofmobile device 100, a flashing or lit light-emitting diode (LED) ofmobile device 100, etc.), an audio alert (e.g., by a speaker of mobiledevice 100), a vibration of mobile device 100 (e.g., by a piezoelectricelement within the main body of mobile device 100), and/or the like.

For example, whenever and for as long as detachable mini-camera 150 isdetached from mobile device 100, the top, bottom, or corner of graphicaluser interface 400 may comprise a graphical element which indicates thatdetachable mini-camera 150 is detached. Alternatively or additionally,whenever and for as long as detachable mini-camera 150 is detached frommobile device 100, a LED in mobile device 100 may stay lit or flash atpredetermined intervals (e.g., every few seconds).

Additionally or alternatively, whenever and for as long as detachablemini-camera 150 is detached from mobile device 100, the mobileapplication may determine or estimate a distance between detachedmini-camera 150 and mobile device 100. For example, the mobileapplication could estimate the distance based on a signal strength(e.g., received signal strength indication (RSSI)) of the wirelesssignal received from detached mini-camera 15, with stronger signalstrengths indicative of a closer distance and weaker signal strengthsindicative of a farther distance. Alternatively, detached mini-camera150 may comprise a GPS receiver (e.g., comprising flex cable antenna362) and may wirelessly transmit its GPS location, obtained via the GPSreceiver, to the mobile application at predetermined intervals. In thiscase, the mobile application may acquire the GPS location of mobiledevice 100 (e.g., via a GPS receiver in mobile device 100) and calculatethe distance between the GPS location of detached mini-camera 150 andthe GPS location of mobile device 100. Regardless of how the distancebetween detached mini-camera 150 and mobile device 100 is determined orestimated, the mobile application may activate an alert whenever thedistance exceeds a predetermined threshold, indicating that the distanceis approaching the maximum limit of the wireless communication range(e.g., 50 feet) supported by the wireless technology being used bytransceiver 360. While the distance is below the predeterminedthreshold, the mobile application does not activate the alert. In anembodiment, the alert may be visual, auditory, and/or vibratory anddesigned to be very likely to attract the user's attention. For example,the alert may comprise flashing a bright light using an LED and/or otherlight source of mobile device 100, outputting a shrill sound from aspeaker of mobile device 100, strongly vibrating the housing of mobiledevice 100, and/or the like. The alert may also comprise displaying aprominent prompt, on the display of mobile device 100 (e.g., withingraphical user interface 400), that requests the user to reattachdetached mini-camera 150 to mobile device 100.

In an embodiment, multiple levels of alerts may be used. For example,when detachable mini-camera 150 is in the detached state, the mobileapplication may display a non-obtrusive visual indication withingraphical user interface 400. If the distance between detachedmini-camera 150 and mobile device 100 reaches a first predeterminedthreshold, the mobile application may provide a less obtrusive visualindication and/or a weak auditory and/or vibratory alert. Then, if thedistance between detached mini-camera 150 and mobile device 100 reachesa second predetermined threshold, that is greater than the firstpredetermined threshold, the mobile application may prominently warn theuser (e.g., by prompting the user to reattach detached mini-camera 150)within graphical user interface 400 (e.g., by using the entire graphicaluser interface 400 for the prompt) and/or provide a strong auditoryand/or vibratory alert. Advantageously, this minimizes the likelihoodthat a user will forget about and lose detached mini-camera 150, whilealso minimizing the annoyance to the user.

2.8. GPS Locator

In an embodiment, the mobile application comprises a GPS trackingfunction for locating a detached mini-camera 150 (e.g., if it is lost).For example, detached mini-camera 150 may comprise a GPS receiver (e.g.,comprising flex cable antenna 362) and may wirelessly transmit its GPSlocation, obtained via the GPS receiver, to the mobile application atpredetermined intervals. The mobile application may store the mostrecent GPS location or a rolling window of a predetermined number (e.g.,ten) of the most recent GPS locations reported by detached mini-camera150. Thus, even if detached mini-camera 150 is outside the range ofwireless communication, the mobile application can utilize the mostrecent known location of detached mini-camera 150 to guide the user todetached mini-camera 150. Advantageously, this minimizes the likelihoodthat detached mini-camera 150 will be permanently lost.

Specifically, if the user has lost detached mini-camera 150, the usermay navigate to a GPS-tracking screen within graphical user interface400 of the mobile application. The GPS-tracking screen may comprise avirtual map of a vicinity of mobile device 100. The mobile applicationmay acquire the current GPS location of mobile device 100 (e.g., via aGPS receiver in mobile device 100) and mark the current GPS location ofmobile device 100 on the virtual map. In addition, the mobileapplication may retrieve the most recent known GPS location of detachedmini-camera 150 from memory and mark the most recent known GPS locationof detached mini-camera 150 on the virtual map. The GPS-tracking screenmay also comprise directions to guide the user from the current locationof mobile device 100 to the most recent known location of detachedmini-camera 150.

If detached mini-camera 150 is stationary, it should still be at itsmost recent known location. However, if detached mini-camera 150 is notstationary, it may no longer be at the most recent known location.However, the most recent known location at least provides a startingpoint for locating detached mini-camera 150. For example, it may be thatdetached mini-camera 150 is still nearby the most recent known location.In this case, when the user brings mobile device 100 to the most recentknown location, if detached mini-camera 150 is close enough to be withinwireless communication range with mobile device 100 and assuming thattransceiver 360 is still being powered (e.g., by rechargeable battery350), the mobile application should receive an updated GPS location fromtransceiver 360. The mobile application may then update the most recentknown GPS location of detached mini-camera 150 on the virtual map in theGPS-tracking screen and/or update the directions, to guide the user tothe updated GPS location.

3. Example Usage

One example usage of detachable mini-camera 150 and the associatedmobile application will now be described. The described example issimply one illustration of how a typical user might utilize thedisclosed embodiments for a specific purpose, and should not beconsidered limiting in any manner.

The user may start by detaching detachable mini-camera 150 from mobiledevice 100, for example, by sliding detachable mini-camera 150 out ofsocket 110. The user may fasten detached mini-camera 150 to the user'sperson, for example, by clipping it to the user's shirt, hat, orsunglasses. In an embodiment, when detached from mobile device 100,detachable mini-camera 150 may seamlessly (i.e., without interruption)transition from being powered by the battery of mobile device 100 tobeing powered by rechargeable battery 350. Furthermore, in response tobeing detached from mobile device 100, detached mini-camera 150 mayautomatically activate and power up transceiver 360 to begin wirelesslycommunicating with mobile device 100.

The user may also activate the mobile application. For example, the usermay select an icon associated with the mobile application within agraphical user interface of mobile device 100 to execute the mobileapplication in the foreground of mobile device 100. When firstactivated, the mobile application may display a main screen (e.g., themain screen illustrated in FIG. 4A). Once activated, the user cannavigate through one or more screens of the mobile application tocontrol detached mini-camera 150 and/or specify settings for detachedmini-camera 150. As discussed elsewhere herein, the mobile applicationmay perform the alert function to prevent detached mini-camera 150 frombeing lost.

If the user wishes to take a photograph, the user may navigate to aphotograph screen (e.g., the photograph screen illustrated in FIG. 4B)to transition the mobile application to a photography mode. The user mayutilize inputs within the photograph screen to zoom in, zoom out, rotatea photographic camera 154 in detached mini-camera 150 (e.g., left,right, up, and/or down), and/or specify other settings. In response tothese inputs, the mobile application wirelessly transmits one or morecontrol commands to detached mini-camera 150, and, in response toreceiving the control command(s), detached mini-camera 150 adjusts thecomponents of detached mini-camera 150 (e.g., camera 154, flash 158,etc.) according to the control command(s). Once the user has specifiedall the desired settings, the user may select an input for capturing aphotograph. In response to this input, the mobile application wirelesslytransmits a control command for capturing a photograph to detachedmini-camera 150, and, in response to receiving the control command,detached mini-camera 150 captures the photograph, and wirelesslytransmits the photograph to the mobile application. Upon receiving thephotograph from detached mini-camera 150, the mobile application maydisplay the photograph on a display of mobile device 100 and/or save thephotograph to a memory of mobile device 100 (e.g., in association with agallery or camera roll).

As another example, if the user wishes to record a video, the user maynavigate to a video screen (e.g., the video screen illustrated in FIG.4C) to transition the mobile application to a video mode. The user mayselect an input within the video screen for starting a video recording.In response to this input, the mobile application wirelessly transmits acontrol command for starting the video recording to detached mini-camera150, and, in response to receiving the control command, detachedmini-camera 150 begins capturing image frames and wirelesslytransmitting those image frames to mobile application, which accumulateseach received image frame in a memory of mobile device 100. Once theuser has decided to end the video recording, the user may select aninput for ending the video recording (e.g., the same input that was usedto start the video recording). In response to this input, the mobileapplication wirelessly transmits a control command for ending the videorecording to detached mini-camera 150, and, in response to receiving thecontrol command, detached mini-camera 150 stops capturing image frameswhile wirelessly transmitting any previously untransmitted image framesto mobile application. Once all image frames have been received or asthe image frames are received, the mobile application saves theaccumulated image frames as a video file in the memory of mobile device100 (e.g., in association with a gallery or camera roll). Before orduring the video recording, the user may utilize inputs within the videoscreen to zoom in, zoom out, rotate a video camera 154 in detachedmini-camera 150 (e.g., left, right, up, and/or down), and/or specifyother settings. In response to these inputs, the mobile applicationwirelessly transmits one or more control commands to detachedmini-camera 150, and, in response to receiving the control command(s),detached mini-camera 150 adjusts the components of detached mini-camera150 (e.g., camera 154) according to the control command(s).

As yet another example, if the user wishes to live stream, the user maynavigate to a live-stream screen (e.g., the live-stream screenillustrated in FIG. 4D) to transition the mobile application to alive-stream mode. The user may select an input within the live-streamscreen for starting a live stream. In response to this input, the mobileapplication wirelessly transmits a control command for starting the livestream to detached mini-camera 150, and, in response to receiving thecontrol command, detached mini-camera 150 begins capturing image framesand wirelessly transmitting those image frames to mobile application,which relays the image frames (e.g., with or without intermediateprocessing) to another device or sharing platform (e.g., social mediaplatform). Once the user has decided to end the live stream, the usermay select an input for ending the live stream (e.g., the same inputthat was used to start the live stream). In response to this input, themobile application wirelessly transmits a control command for ending thelive stream to detached mini-camera 150, and, in response to receivingthe control command, detached mini-camera 150 stops capturing imageframes. Before or during the live stream, the user may utilize inputswithin the live-stream screen to zoom in, zoom out, rotate a videocamera 154 in detached mini-camera 150 (e.g., left, right, up, and/ordown), and/or specify other settings. In response to these inputs, themobile application wirelessly transmits one or more control commands todetached mini-camera 150, and, in response to receiving the controlcommand(s), detached mini-camera 150 adjusts the components of detachedmini-camera 150 (e.g., camera 154) according to the control command(s).

Prior to or during the live stream, the user may also create a new groupof contacts (e.g., via the grouping screen illustrated in FIG. 4E) orspecify an existing group of contacts (e.g., via the grouping screenillustrated in FIG. 4E or via an input in the live-stream screen) to beinvited to view the live stream. If a group is selected, the mobileapplication may send an invitation (e.g., SMS or MMS message) to eachcontact in the group with a link (e.g., hyperlink) to the resource,associated with the live stream, on a sharing platform (e.g., a socialmedia platform) or other information for joining the live stream.Contacts who select the link or otherwise accept the invitation may viewthe live stream via the sharing platform (e.g., using their credentialsto log in to their respective user accounts on the sharing platform ifthe live stream is private, or without authentication if the live streamis public).

If the user wishes to use the object tracking function of the mobileapplication (e.g., to track a person of interest in a video recording orlive stream), the user may navigate to an object-identification screen(e.g., the object-identification screen illustrated on the left side inFIG. 4F). The user may select an input within the capture screen toselect or capture a photograph of the object of interest, and identifythe object of interest within the photograph. In response to theidentification of the object of interest, the mobile application willgenerate a reference feature vector to be used for tracking the objectof interest. The user may then (contemporaneously or at some much latertime) navigate to the video screen (e.g., the video screen illustratedin FIG. 4C) or the live-stream screen (e.g., the live-stream screenillustrated in FIG. 4D) and begin a video recording or live stream, asdiscussed above. During the video recording or live stream, the mobileapplication will compare features in the captured image frames to thereference feature vector to recognize the object of interest within thecaptured image frames, and control detached mini-camera 150 to rotateand/or otherwise move camera 154 (e.g., left or right, up or down, etc.)to maintain the object of interest within a vicinity of the center ofsubsequent image frames. In this manner, the user can simply detachmini-camera 150 from mobile device 100 and fasten the detachedmini-camera 150 to another object or set the detached mini-camera 150 onanother object, such that the user can watch the action live withouthaving to hold and position mobile device 100.

As a concrete example, a user may wish to live-stream his daughter'ssoccer game to the daughter's grandparents who reside in a differentstate and the daughter's mother who is out of town for a businessmeeting, and therefore, are unable to attend the soccer game in person.However, the user also wishes to relax and enjoy his daughter's soccergame. Using a mobile device 100 with the detachable mini-camera 150 andthe mobile application of disclosed embodiments, the user is able toachieve both objectives. Specifically, the user may use the mobileapplication to create or select a group of contacts (e.g., using thegrouping screen illustrated in FIG. 4E) that consists of the daughter'smother and grandparents (e.g., identified by their respective telephonenumbers). The mobile application will send invitations to the daughter'smother and grandparents which provide each of them with a hyperlink to asocial networking platform, selected by the user (e.g., using thesharing screen illustrated in FIG. 4H), and a resource through which thesoccer game will be live streamed. The user may also use the mobileapplication to capture a photograph of his daughter prior to the gameand identify his daughter's face in the photograph to the mobileapplication for object tracking (e.g., using the object-identificationscreen illustrated on the left side in FIG. 4F). The user may detachdetachable mini-camera 150 from his mobile device 100, fasten detachedmini-camera 150 to his shirt or hat, and use the mobile application tobegin a live stream (e.g., using the live-stream screen illustrated inFIG. 4D). Afterwards, the user may store mobile device 100 in his pocketand watch the game live without having to worry about mobile device 100,detached mini-camera 150, and the mobile application. The mobileapplication will wirelessly communicate with detached mini-camera tocontrol camera 154 in detached mini-camera 150, while detachedmini-camera 150 is clipped to the user's shirt or hat, to track thedaughter on the soccer field, and relay the image data, captured bycamera 154 and representing the live stream, to the social networkingplatform selected by the user, in real time. The social networkingplatform will, in turn, provide the live stream to the daughter'sgrandparents and mother.

If the user wishes to edit a photograph, video recording, or livestream, before, during, or after capture, the user may navigate to anediting screen (e.g., the editing screen illustrated in FIG. 4G). Theuser may select one or more inputs associated with editing options, suchas filters, effects, settings (e.g., brightness, exposure, etc.), and/orthe like, to easily apply image processing to the photograph or to theimage frames of the video recording or live stream.

4. Example Processing Device

FIG. 5 is a block diagram illustrating an example wired or wirelesssystem 500 that may be used in connection with various embodimentsdescribed herein. For example, system 500 may be used as or inconjunction with one or more of the functions, processes, or methods(e.g., to store and/or execute the mobile application or one or moresoftware modules of the mobile application) described herein, and mayrepresent components of mobile device 100, detachable mini-camera 150,and/or other processing devices described herein. System 500 can be asmartphone, a controller for detachable mini-camera 150, or any otherprocessor-enabled device that is capable of wired or wireless datacommunication. Other computing systems and/or architectures may be alsoused, as will be clear to those skilled in the art.

System 500 preferably includes one or more processors, such as processor510. Additional processors may be provided, such as an auxiliaryprocessor to manage input/output, an auxiliary processor to performfloating-point mathematical operations, a special-purpose microprocessorhaving an architecture suitable for fast execution of signal-processingalgorithms (e.g., digital-signal processor), a slave processorsubordinate to the main processing system (e.g., back-end processor), anadditional microprocessor or controller for dual or multiple processorsystems, and/or a coprocessor. Such auxiliary processors may be discreteprocessors or may be integrated with processor 510. Examples ofprocessors which may be used with system 500 include, withoutlimitation, the Pentium® processor, Core i7® processor, and Xeon®processor, all of which are available from Intel Corporation of SantaClara, Calif.

Processor 510 is preferably connected to a communication bus 505.Communication bus 505 may include a data channel for facilitatinginformation transfer between storage and other peripheral components ofsystem 500. Furthermore, communication bus 505 may provide a set ofsignals used for communication with processor 510, including a data bus,address bus, and/or control bus (not shown). Communication bus 505 maycomprise any standard or non-standard bus architecture such as, forexample, bus architectures compliant with industry standard architecture(ISA), extended industry standard architecture (EISA), Micro ChannelArchitecture (MCA), peripheral component interconnect (PCI) local bus,standards promulgated by the Institute of Electrical and ElectronicsEngineers (IEEE) including IEEE 488 general-purpose interface bus (GPM),IEEE 696/S-100, and/or the like.

System 500 preferably includes a main memory 515 and may also include asecondary memory 520. Main memory 515 provides storage of instructionsand data for programs executing on processor 510, such as one or more ofthe functions and/or modules discussed herein. It should be understoodthat programs stored in the memory and executed by processor 510 may bewritten and/or compiled according to any suitable language, includingwithout limitation C/C++, Java, JavaScript, Perl, Visual Basic, .NET,and the like. Main memory 515 is typically semiconductor-based memorysuch as dynamic random access memory (DRAM) and/or static random accessmemory (SRAM). Other semiconductor-based memory types include, forexample, synchronous dynamic random access memory (SDRAM), Rambusdynamic random access memory (RDRAM), ferroelectric random access memory(FRAM), and the like, including read only memory (ROM).

Secondary memory 520 may optionally include an internal medium 525and/or a removable medium 530. Removable medium 530 is read from and/orwritten to in any well-known manner. Removable storage medium 530 maybe, for example, a magnetic tape drive, a compact disc (CD) drive, adigital versatile disc (DVD) drive, other optical drive, a flash memorydrive, and/or the like.

Secondary memory 520 is a non-transitory computer-readable medium havingcomputer-executable code (e.g., disclosed software modules) and/or otherdata stored thereon. The computer software or data stored on secondarymemory 520 is read into main memory 515 for execution by processor 510.

In alternative embodiments, secondary memory 520 may include othersimilar means for allowing computer programs or other data orinstructions to be loaded into system 500. Such means may include, forexample, a communication interface 540, which allows software and datato be transferred from external storage medium 545 to system 500.Examples of external storage medium 545 may include an external harddisk drive, an external optical drive, an external magneto-opticaldrive, and/or the like. Other examples of secondary memory 520 mayinclude semiconductor-based memory, such as programmable read-onlymemory (PROM), erasable programmable read-only memory (EPROM),electrically erasable read-only memory (EEPROM), and flash memory(block-oriented memory similar to EEPROM).

As mentioned above, system 500 may include a communication interface540. Communication interface 540 allows software and data to betransferred between system 500 and external devices (e.g. printers),networks, or other information sources. For example, computer softwareor executable code may be transferred to system 500 from a networkserver via communication interface 540. Examples of communicationinterface 540 include a built-in network adapter, network interface card(NIC), Personal Computer Memory Card International Association (PCMCIA)network card, card bus network adapter, wireless network adapter,Universal Serial Bus (USB) network adapter, modem, a wireless data card,a communications port, an infrared interface, an IEEE 1394 fire-wire,and any other device capable of interfacing system 500 with a network oranother computing device. Communication interface 540 preferablyimplements industry-promulgated protocol standards, such as EthernetIEEE 802 standards, Fiber Channel, digital subscriber line (DSL),asynchronous digital subscriber line (ADSL), frame relay, asynchronoustransfer mode (ATM), integrated digital services network (ISDN),personal communications services (PCS), transmission controlprotocol/Internet protocol (TCP/IP), serial line Internet protocol/pointto point protocol (SLIP/PPP), and so on, but may also implementcustomized or non-standard interface protocols as well.

Software and data transferred via communication interface 540 aregenerally in the form of electrical communication signals 555. Thesesignals 555 may be provided to communication interface 540 via acommunication channel 550. In an embodiment, communication channel 550may be a wired or wireless network, or any variety of othercommunication links. Communication channel 550 carries signals 555 andcan be implemented using a variety of wired or wireless communicationmeans including wire or cable, fiber optics, conventional phone line,cellular phone link, wireless data communication link, radio frequency(“RF”) link, or infrared link, just to name a few.

Computer-executable code (e.g., computer programs, such as the disclosedmobile application, or software modules) is stored in main memory 515and/or secondary memory 520. Computer programs can also be received viacommunication interface 540 and stored in main memory 515 and/orsecondary memory 520. Such computer programs, when executed, enablesystem 500 to perform the various functions of the disclosed embodimentsas described elsewhere herein.

In this description, the term “computer-readable medium” is used torefer to any non-transitory computer-readable storage media used toprovide computer-executable code and/or other data to or within system500. Examples of such media include main memory 515, secondary memory520 (including internal memory 525, removable medium 530, and externalstorage medium 545), and any peripheral device communicatively coupledwith communication interface 540 (including a network information serveror other network device). These non-transitory computer-readable mediaare means for providing executable code, programming instructions,software, and/or other data to system 500.

In an embodiment that is implemented using software, the software may bestored on a computer-readable medium and loaded into system 500 by wayof removable medium 530, I/O interface 535, or communication interface540. In such an embodiment, the software is loaded into system 500 inthe form of electrical communication signals 555. The software, whenexecuted by processor 510, preferably causes processor 510 to performone or more of the processes and functions described elsewhere herein.

In an embodiment, I/O interface 535 provides an interface between one ormore components of system 500 and one or more input and/or outputdevices. Example input devices include, without limitation, sensors,keyboards, touch screens or other touch-sensitive devices, biometricsensing devices, computer mice, trackballs, pen-based pointing devices,and/or the like. Examples of output devices include, without limitation,other processing devices, cathode ray tubes (CRTs), plasma displays,light-emitting diode (LED) displays, liquid crystal displays (LCDs),printers, vacuum fluorescent displays (VFDs), surface-conductionelectron-emitter displays (SEDs), field emission displays (FEDs), and/orthe like. In some cases, an input and output device may be combined,such as in the case of a touch panel display (e.g., in a smartphone,tablet, or other mobile device).

System 500 may also include optional wireless communication componentsthat facilitate wireless communication over a voice network and/or adata network (e.g., in the case of mobile device 100). The wirelesscommunication components comprise an antenna system 570, a radio system565, and a baseband system 560. In system 500, radio frequency (RF)signals are transmitted and received over the air by antenna system 570under the management of radio system 565.

In an embodiment, antenna system 570 may comprise one or more antennaeand one or more multiplexors (not shown) that perform a switchingfunction to provide antenna system 570 with transmit and receive signalpaths. In the receive path, received RF signals can be coupled from amultiplexor to a low noise amplifier (not shown) that amplifies thereceived RF signal and sends the amplified signal to radio system 565.

In an alternative embodiment, radio system 565 may comprise one or moreradios that are configured to communicate over various frequencies. Inan embodiment, radio system 565 may combine a demodulator (not shown)and modulator (not shown) in one integrated circuit (IC). Thedemodulator and modulator can also be separate components. In theincoming path, the demodulator strips away the RF carrier signal leavinga baseband receive audio signal, which is sent from radio system 565 tobaseband system 560.

If the received signal contains audio information, then baseband system560 decodes the signal and converts it to an analog signal. Then thesignal is amplified and sent to a speaker. Baseband system 560 alsoreceives analog audio signals from a microphone. These analog audiosignals are converted to digital signals and encoded by baseband system560. Baseband system 560 also encodes the digital signals fortransmission and generates a baseband transmit audio signal that isrouted to the modulator portion of radio system 565. The modulator mixesthe baseband transmit audio signal with an RF carrier signal, generatingan RF transmit signal that is routed to antenna system 570 and may passthrough a power amplifier (not shown). The power amplifier amplifies theRF transmit signal and routes it to antenna system 570, where the signalis switched to the antenna port for transmission.

Baseband system 560 is also communicatively coupled with processor 510,which may be a central processing unit (CPU). Processor 510 has accessto data storage areas 515 and 520. Processor 510 is preferablyconfigured to execute instructions (i.e., computer programs, such as thedisclosed application, or software modules) that can be stored in mainmemory 515 or secondary memory 520. Computer programs can also bereceived from baseband processor 560 and stored in main memory 510 or insecondary memory 520, or executed upon receipt. Such computer programs,when executed, enable system 500 to perform the various functions of thedisclosed embodiments.

The above description of the disclosed embodiments is provided to enableany person skilled in the art to make or use the invention. Variousmodifications to these embodiments will be readily apparent to thoseskilled in the art, and the general principles described herein can beapplied to other embodiments without departing from the spirit or scopeof the invention. Thus, it is to be understood that the description anddrawings presented herein represent a presently preferred embodiment ofthe invention and are therefore representative of the subject matterwhich is broadly contemplated by the present invention. It is furtherunderstood that the scope of the present invention fully encompassesother embodiments that may become obvious to those skilled in the artand that the scope of the present invention is accordingly not limited.

Combinations, described herein, such as “at least one of A, B, or C,”“one or more of A, B, or C,” “at least one of A, B, and C,” “one or moreof A, B, and C,” and “A, B, C, or any combination thereof” include anycombination of A, B, and/or C, and may include multiples of A, multiplesof B, or multiples of C. Specifically, combinations such as “at leastone of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B,and C,” “one or more of A, B, and C,” and “A, B, C, or any combinationthereof” may be A only, B only, C only, A and B, A and C, B and C, or Aand B and C, and any such combination may contain one or more members ofits constituents A, B, and/or C. For example, a combination of A and Bmay comprise one A and multiple B's, multiple A's and one B, or multipleA's and multiple B's.

What is claimed is:
 1. A mobile device comprising: a main bodycomprising a battery, a first wireless transceiver, a socket, at leastone hardware processor, a memory, and a mobile application stored in thememory; and a detachable mini-camera configured to attach to the socketand detach from the socket, wherein the detachable mini-camera comprisesat least one camera, a rechargeable battery configured to charge fromthe battery in the main body when the detachable mini-camera is attachedto the socket, and a second wireless transceiver configured towirelessly communicate with the first wireless transceiver in the mainbody when the detachable mini-camera is detached from the socket;wherein the mobile application is configured to, when executed by the atleast one hardware processor in the main body, when the detachablemini-camera is detached from the socket, wirelessly communicate with thedetachable mini-camera, via the first and second wireless transceivers,to control the detachable mini-camera and receive image data captured bythe detachable mini-camera.
 2. The mobile device of claim 1, wherein thedetachable mini-camera further comprises at least one sensor and atleast one flash.
 3. The mobile device of claim 1, wherein the at leastone camera consists of a single camera configured to capture photographsand video.
 4. The mobile device of claim 1, wherein the at least onecamera comprises a first camera dedicated to capturing photographs, anda second camera dedicated to capturing video, comprising a plurality ofimage frames.
 5. The mobile device of claim 1, wherein the at least onecamera comprises: a mini-camera device; and at least one motor poweredby the rechargeable battery in the detachable mini-camera and configuredto rotate the mini-camera within a range of rotation around at least oneaxis.
 6. The mobile device of claim 5, wherein the at least one camerafurther comprises a rod, wherein the at least one motor comprises aball-and-axis motor that is attached to a first end of the rod, whereinthe mini-camera device is attached to a second end of the rod that isopposite to the first end, and wherein the ball-and-axis motor isconfigured to, when activated, rotate the rod, so as to rotate themini-camera within the range of rotation around a first axis that iscoincident with a longitudinal axis of the rod.
 7. The mobile device ofclaim 6, wherein the mini-camera device comprises an imaging face on afront side and a motor on a rear side, opposite the imaging face, andwherein the motor is configured to rotate the imaging face within arange of rotation around a second axis that is orthogonal to thelongitudinal axis of the rod.
 8. The mobile device of claim 5, whereinthe mobile application is configured to: generate a graphical userinterface that comprises one or more inputs for moving the mini-cameradevice; and, in response to receiving a user operation of at least oneof the one or more inputs, transmit a control command from the firstwireless transceiver in the main body to the second wireless transceiverin the detachable mini-camera, so as to actuate the at least one motorto rotate the mini-camera device in accordance with the control command.9. The mobile device of claim 8, wherein the mobile application isfurther configured to: generate a graphical user interface thatcomprises one or more inputs for specifying an object in a photograph;and, when an object is specified, generate a reference representation ofthe object, and during a subsequent video recording or live stream inwhich the mobile application receives a plurality of image frames fromthe detachable mini-camera, detect the object in one or more of theplurality of image frames, and, in response to detecting the object,transmit a control command from the first wireless transceiver in themain body to the second wireless transceiver in the detachablemini-camera, so as to actuate the at least one motor to rotate themini-camera device to track the object.
 10. The mobile device of claim1, wherein the mobile application is configured to: generate a graphicaluser interface that comprises a real-time-view region and at least oneinput for one or more of capturing a photograph, initiating a videorecording, and initiating a live stream, wherein the real-time-viewregion comprises real-time image data captured by the detachablemini-camera and wirelessly transmitted from the second wirelesstransceiver in the detachable mini-camera to the first wirelesstransceiver in the main body; and, in response to receiving a useroperation of the at least one input, transmit a control command from thefirst wireless transceiver in the main body to the second wirelesstransceiver in the detachable mini-camera, so as to actuate the at leastone camera in the detachable mini-camera according to the controlcommand.
 11. The mobile device of claim 10, wherein the mobileapplication is configured to, when the user operation of the at leastone input is to capture a photograph: generate the control command tocapture the photograph; receive the photograph from the detachablemini-camera via a wireless communication from the second wirelesstransceiver to the first wireless transceiver; and store the receivedphotograph in the memory in the main body.
 12. The mobile device ofclaim 10, wherein the mobile application is configured to, when the useroperation of the at least one input is to initiate a video recording:generate the control command to initiate the video recording; during thevideo recording, receive a plurality of image frames from the detachablemini-camera via a wireless communication from the second wirelesstransceiver to the first wireless transceiver; and store the receivedplurality of image frames in the memory in the main body as a videofile.
 13. The mobile device of claim 10, wherein the mobile applicationis configured to, when the user operation of the at least one input isto initiate a live stream: generate the control command to initiate thelive stream; and, during the live stream, receive a plurality of imageframes from the detachable mini-camera via a wireless communication fromthe second wireless transceiver to the first wireless transceiver, andrelay the plurality of image frames to a sharing platform via at leastone wireless cellular network.
 14. The mobile device of claim 13,wherein the mobile application is further configured to: generate agraphical user interface that comprises one or more inputs foridentifying a group of one or more contacts; and, for each of the one ormore contacts in the group, transmit an invitation to the contact,wherein the invitation comprises information for viewing the livestream.
 15. The mobile device of claim 13, wherein the mobileapplication is further configured to generate a graphical user interfacethat comprises one or more inputs configured to receive a user selectionof the sharing platform.
 16. The mobile device of claim 1, wherein themain body further comprises: a front surface comprising a touch paneldisplay; and a rear surface comprising the socket, wherein the rearsurface is on an opposite side of the main body as the front surface.